@grindtildeath @sebalix @ajaniszewska-dev @JuMiSanAr @pedrobaeza maybe you want to have a look since you worked in the linked PRs?

I just edited a bit the commit messages in order to follow https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#71commit-message.

Thanks for the review!

This has provoked is done headaches, as the compute is launched on update time

I guess that's the usual behavior when a new stored computed field is added, why is this case different?
Sorry I didn't know about the headaches, I can't find any reference to this in the linked PRs.

I mean that you should provide a init hook or auto_init override for pre-creating the DB schema and fast-populate data for existing records.

I mean that you should provide a init hook or auto_init override for pre-creating the DB schema and fast-populate data for existing records.

Thanks for the hint, so at upgrade time the computed fields should be populated with an optimized calculation (you mean like SQL queries?) instead of letting the field compute itself, did I understand that correctly?

Correct.

I tried to do a SQL query for computing all the values in _auto_init but it's a hell of relations of *2many fields (created_production_ids, move_orig_ids, mrp_production_ids); I tried to optimize the compute method itself, would you have another look?